System for validated tracking and management of events associated with equipment during lifetime usage

ABSTRACT

Validated tracking and managing of events associated with equipment during a usage lifetime. Equipment is registered within a distributed register/ledger of a distributed trust network according to an equipment identifier and subsequently events related to the equipment are registered and managed within the distributed register/ledger during the usage lifetime. Such events include resource arrangement-related events and property-right-related events. In addition, logic may be included in the distributed register/leger that triggers various actions in response to the events.

FIELD OF THE INVENTION

The present invention is generally directed to data verification and,more specifically, providing verified tracking and managing of equipmentduring the useful lifetime of the equipment.

BACKGROUND

Certain events related to equipment, such as collateralized and/ortitled equipment, such as automobiles, boats, industrial equipment, andthe like require that information be verified in order for theoccurrence of certain events related to the equipment. In many instancessuch information is difficult, if not impossible, to obtain. In furtherinstances the verification of such information requires the physicalpresence or attestation of parties to the events. Such processing isoften wrought with delays and other inefficiencies.

Therefore, a need exits to provide systems, computer-implementedmethods, computer program products and the like for validated trackingof managing events associated with equipment during the entirety of theusage period, otherwise referred to as the usage lifetime. Specifically,the desired systems and the like should validate the occurrence of anyevents-related to the equipment and manage the occurrence of any actionsthat are triggered in response to the verified events.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

Embodiments of the present invention address the above needs and/orachieve other advantages by providing for validated tracking andmanagement of events associated with equipment during the equipment'susage lifetime. In specific embodiments of the invention, the eventsinclude resource arrangement-related events associated with resourcearrangements related to the equipment and property right-related eventsassociated with changing in property rights related to the equipment areregistered as data blocks within a distributed register/ledger of adistributed trust computing network. The registering of the eventswithin the distributed trust computing network serves as a source oftruth (i.e., verification that the events have, in fact, occurred or areotherwise authentic).

In further embodiments of the invention, a virtual registration objectis generated including a virtual registration identifier and associatedinformation. The virtual registration object is associated with theequipment throughout the usage lifetime and provides for automatedequipment registrations as the equipment is transferred/moved from oneregistration jurisdiction to another registration jurisdiction. In thisregard, the virtual registration object is registered in the distributedtrust computing network by creating a data block within the distributedregister/ledger that verifies the authenticity of the virtualregistration object and its association with the previously registeredequipment.

Further, in specific embodiments, the invention is further capable oftracking other events associated with the equipment, such as resourcearrangement-related events and the like. For example, the invention maytrack the occurrence of a change in property rights (e.g., tiletransfer) associated with the equipment and register the event in thedistributed register/ledger. Further, the distributed ledger may beconfigured with logic that recognizes the event and, in response,performs one or more predetermined actions (e.g., satisfying outstandingobligations associated with the resource arrangement, transferringtitle, resource transfers associated with registration, maintenance,indemnification or the like).

Moreover, embodiments of the present invention are able to provideaccess to the validated information stored on the distributedregister/ledger to a plurality of different entities on a need-to-knowbasis. In this regard, designated entities may be provided access tolimited portions (i.e., specified data blocks) of the distributedregister/ledger based on system operator selection.

A system for validated tracking of events associated with equipmentdefines first embodiments of the invention. The system includes adistributed trust computing network that includes a plurality ofdecentralized nodes. Each decentralized node has a first memory and atleast one first processing device in communication with the firstmemory. The first memory of the decentralized nodes is configured tostore a plurality of distributed registers/ledgers, each distributedregister comprising a plurality of blocks of data.

The system additionally includes a computing platform disposed in adistributed computing network and including a second memory and at leastone second processing device in communication with the second memory.The second memory stores instructions that are executable by the atleast one second processing device. The instructions are configured toreceive indication of a resource arrangement associated with anequipment and, in response, initiate generation of one of the pluralityof distributed registers/ledgers. The distributed register/ledger storesan equipment identifier, resource arrangement information and equipmentinformation. The instructions are further configured to determine thatthe equipment has incurred a location-changing event and, in response,register the location-changing event within the distributed trustcomputing network by creating a first block within the distributedregister that includes information associated with the location-changingevent. The registering of the location-changing event within thedistributed trust computing network provides for validating authenticityof the location-changing event.

In specific embodiments of the system, the instructions are furtherconfigured to determine an occurrence of a resource arrangement-relatedevent, and, in response, register the resource arrangement-related eventwith the distributed trust computing network by creating a second blockwithin the distributed register that includes information associatedwith the resource arrangement-related event. The registering of theresource arrangement-related event within the distributed trustcomputing network provides for validating authenticity of the resourcearrangement-related event. In further specific embodiments of thesystem, the resource arrangement-related event is a transfer in title ofthe equipment from a resource recipient of the resource arrangement to athird-party entity. In such embodiments of the system, the instructionsmay be further configured to, in response to the transfer of title,initiate a final resource transfer from the resource recipient to aresource provider of the resource arrangement to complete the resourcearrangement. In other such embodiments of the system, the instructionsmay be further configured to, in response to the transfer of title,generate documentation associated with the transfer of title andregister the documentation with the distributed trust computing networkby creating a third block within the distributed register that includesinformation associated with the documentation.

In specific embodiments of the system, the location-changing event mayinclude one of (i) physical movement of the equipment from a firstlocation associated with an equipment provider to a second locationassociated with a resource recipient of the resource arrangement, (ii)physical movement of the equipment within a geo-fenced region defined bya location associated with a resource recipient of the resourcearrangement, (iii) physical movement of the equipment outside of ageo-fenced region defined by a location associated with a resourcerecipient of the resource arrangement, and (iv) physical movement of theequipment from a first location associated with a first resourcerecipient of the resource arrangement to a second location associatedwith a transferred resource recipient of the resource arrangement.

In still further specific embodiments of the system, the instructionsare further configured to provide a resource recipient of the resourcearrangement access to at least a portion of the distributed register toverify a current location of the equipment. While in other relatedembodiments of the invention, the instructions are further configured toprovide an insurer of the equipment access to at least a portion of thedistributer register to verify a current location of the equipment.Moreover, in other embodiments of the system, the instructions arefurther configured to provide a resource provider associated with asecond tier resource arrangement, conducted for purposes of a change intitle, access to at least a portion of the distributed register toverify a chain of title in the equipment.

A computer-implemented method for validated tracking of eventsassociated with equipment defines second embodiments of the invention.The method is executed by one or more computer processor devices. Themethod includes receiving indication of a resource arrangementassociated with an equipment, and, in response, initiating generation ofa distributed register stored within nodes of a distributed trustcomputing network. The distributed register stores an equipmentidentifier, resource arrangement information and equipment information.The method further includes determining that the equipment has incurreda location-changing event, and, in response, registering thelocation-changing event within the distributed trust computing networkby creating a first block within the distributed register that includesinformation associated with the location-changing event. The registeringof the location-changing event within the distributed trust computingnetwork provides for validating authenticity of the location-changingevent.

In specific embodiments the method further includes determining anoccurrence of a resource arrangement-related event and, in response,registering the resource arrangement-related event with the distributedtrust computing network by creating a second block within thedistributed register that includes information associated with theresource arrangement-related event. The registering of the resourcearrangement-related event within the distributed trust computing networkprovides for validating authenticity of the of the resourcearrangement-related event. In such embodiments of the method, theresource arrangement-related event may be a transfer in title of theequipment from a resource recipient of the resource arrangement to athird-party entity. In such embodiments the method may further include,in response to the transfer of title, initiating a final resourcetransfer from the resource recipient to a resource provider of theresource arrangement to complete the resource arrangement. In other suchembodiments the method may further include, in response to the transferof title, generating documentation associated with the transfer oftitle, and registering the documentation with the distributed trustcomputing network by creating a third block within the distributedregister that includes information associated with the documentation.

In specific embodiments of the method, the location-changing event ischosen from the group comprising of (i) physical movement of theequipment from a first location associated with an equipment provider toa second location associated with a resource recipient of the resourcearrangement, (ii) physical movement of the equipment within a geo-fencedregion defined by a location associated with a resource recipient of theresource arrangement, (iii) physical movement of the equipment outsideof a geo-fenced region defined by a location associated with a resourcerecipient of the resource arrangement, and (iv) physical movement of theequipment from a first location associated with a first resourcerecipient of the resource arrangement to a second location associatedwith a transferred resource recipient of the resource arrangement.

A computer program product including a non-transitory computer-readablemedium defines third embodiments of the invention. The computer-readablemedium includes a first set of codes for causing a computer processor toreceive indication of a resource arrangement associated with anequipment and a second set of codes for causing a computer processor toinitiate generation of a distributed register stored within nodes of adistributed trust computing network, wherein the distributed registerstores an equipment identifier, resource arrangement information andequipment information. In addition, the computer-readable mediumincludes a third set of codes for causing a computer processor todetermine that the equipment has incurred a location-changing event anda fourth set of codes for causing a computer processor to register thelocation-changing event within the distributed trust computing networkby creating a first block within the distributed register that includesinformation associated with the location-changing event. The registeringof the location-changing event within the distributed trust computingnetwork provides for validating authenticity of the of thelocation-changing event.

In specific embodiments of the computer program product, thecomputer-readable medium additionally includes a fifth set of codes forcausing a computer processor to determine an occurrence of a resourcearrangement-related event, and a sixth set of codes for causing acomputer processor to register the resource arrangement-related eventwith the distributed trust computing network by creating a second blockwithin the distributed register that includes information associatedwith the resource arrangement-related event. The registering of theresource arrangement-related event within the distributed trustcomputing networks provides for validating authenticity of the of theresource arrangement-related event. In such specific embodiments of thecomputer program product, the resource arrangement-related event may bea transfer in title of the equipment from a resource recipient of theresource arrangement to a third-party entity. In such embodiments of thecomputer program product, the computer-readable medium may furtherinclude a seventh set of codes configured to cause a computer processorto, in response to the transfer of title, initiating a final resourcetransfer from the resource recipient to a resource provider of theresource arrangement to complete the resource arrangement. In other suchembodiments of the computer program product, the computer-readablemedium further includes a seventh set of codes for causing a computerprocessor to, in response to the transfer of title, generatedocumentation associated with the transfer of title, and register thedocumentation with the distributed trust computing network by creating athird block within the distributed register that includes informationassociated with the documentation.

In specific embodiments of the computer program product, thelocation-changing event is chosen from the group comprising of (i)physical movement of the equipment from a first location associated withan equipment provider to a second location associated with a resourcerecipient of the resource arrangement, (ii) physical movement of theequipment within a geo-fenced region defined by a location associatedwith a resource recipient of the resource arrangement, (iii) physicalmovement of the equipment outside of a geo-fenced region defined by alocation associated with a resource recipient of the resourcearrangement, and (iv) physical movement of the equipment from a firstlocation associated with a first resource recipient of the resourcearrangement to a second location associated with a transferred resourcerecipient of the resource arrangement.

Thus, according to embodiments of the invention, which will be discussedin greater detail below, the present invention provides for tracking andmanaging of events associated with equipment during a usage lifetime.The invention provides for registering an equipment identifier within adistributed register/ledger of a distributed trust network andsubsequently registering and managing events associated with theequipment during the usage lifetime. In specific embodiments of theinvention, such events include resource arrangement-related events andproperty-right-related events. In addition, logic may be included in thedistributed register/leger that triggers various actions in response tothe events.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the disclosure in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 is a schematic diagram of a system for validating tracking ofevents associated with equipment during a resource arrangement, inaccordance with some embodiments of the present invention;

FIG. 2 is a schematic diagram of a system for validating tracking andmanaging of events associated with equipment during a usage lifetime, inaccordance with some embodiments of the present invention;

FIG. 3 is a schematic diagram of a distributed trust computing network,in accordance with embodiments of the present invention;

FIG. 4 is a schematic diagram of systems of the present inventionhighlighting various entities being provided access to data stored onthe distributed register/ledger, in accordance with embodiments of thepresent invention;

FIG. 5 is a block diagram of a computing platform configured forvalidated tracking of events associated with equipment during a resourcearrangement, in accordance with some embodiments of the presentinvention;

FIG. 6 is a block diagram of a computing platform configured forvalidated tracking and managing of events associated with equipmentduring a usage lifetime, in accordance with some embodiments of thepresent invention;

FIG. 7 is schematic/flow diagram illustrating various exemplarylocation-changing events incurred by equipment, in accordance withembodiments of the present invention;

FIG. 8 is a flow diagram of a method for validating tracking of eventsassociated with equipment during a resource arrangement, in accordancewith some embodiments of the present invention; and

FIG. 9 is flow diagram of a method for validating tracking and managingof events associated with equipment during a usage lifetime, inaccordance with some embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

As will be appreciated by one of skill in the art in view of thisdisclosure, the present invention may be embodied as a system, a method,a computer program product or a combination of the foregoing.Accordingly, embodiments of the present invention may take the form ofan entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.), or anembodiment combining software and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program productcomprising a computer-usable storage medium having computer-usableprogram code/computer-readable instructions embodied in the medium.

Any suitable computer-usable or computer-readable medium may beutilized. The computer usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, ordevice. More specific examples (e.g., a non-exhaustive list) of thecomputer-readable medium would include the following: an electricalconnection having one or more wires; a tangible medium such as aportable computer diskette, a hard disk, a time-dependent access memory(RAM), a read-only memory (ROM), an erasable programmable read-onlymemory (EPROM or Flash memory), a compact disc read-only memory(CD-ROM), or other tangible optical or magnetic storage device.

Computer program code/computer-readable instructions for carrying outoperations of embodiments of the present invention may be written in anobject oriented, scripted or unscripted programming language such asJAVA, PERL, SMALLTALK, C++, PYTHON or the like. However, the computerprogram code/computer-readable instructions for carrying out operationsof the invention may also be written in conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages.

Embodiments of the present invention are described below with referenceto flowchart illustrations and/or block diagrams of methods or systems.It will be understood that each block of the flowchart illustrationsand/or block diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the instructions, which execute by theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instructions, whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational events to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions, which execute on the computer or other programmableapparatus, provide events for implementing the functions/acts specifiedin the flowchart and/or block diagram block or blocks. Alternatively,computer program implemented events or acts may be combined withoperator or human implemented events or acts in order to carry out anembodiment of the invention.

As the phrase is used herein, a processor may be “configured to” performor “configured for” performing a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing particular computer-executable programcode embodied in computer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

Thus, according to embodiments of the invention, which will be describedin more detail below, systems, methods and computer program products aredisclosed for validated tracking and management of events associatedwith equipment during the equipment's usage lifetime. In specificembodiments of the invention, the events include resourcearrangement-related events associated with resource arrangements relatedto the equipment and property right-related events associated withchanging in property rights related to the equipment are registered asdata blocks within a distributed register/ledger of a distributed trustcomputing network. The registering of the events within the distributedtrust computing network serves as a source of truth (i.e., verificationthat the events have, in fact, occurred or are otherwise authentic).

In further embodiments of the invention, a virtual registration objectis generated including a virtual registration identifier and associatedinformation. The virtual registration object is associated with theequipment throughout the usage lifetime and provides for automatedequipment registrations as the equipment is transferred/moved from oneregistration jurisdiction to another registration jurisdiction. In thisregard, the virtual registration object is registered in the distributedtrust computing network by creating a data block within the distributedregister/ledger that verifies the authenticity of the virtualregistration object and its association with the previously registeredequipment.

Further, in specific embodiments, the invention is further capable oftracking other events associated with the equipment, such as resourcearrangement-related events and the like. For example, the invention maytrack the occurrence of a change in property rights (e.g., tiletransfer) associated with the equipment and register the event in thedistributed register/ledger. Further, the distributed ledger may beconfigured with logic that recognizes the event and, in response,performs one or more predetermined actions (e.g., satisfying outstandingobligations associated with the resource arrangement, transferringtitle, resource transfers associated with registration, maintenance,indemnification or the like).

Moreover, embodiments of the present invention are able to provideaccess to the validated information stored on the distributedregister/ledger to a plurality of different entities on a need-to-knowbasis. In this regard, designated entities may be provided access tolimited portions (i.e., specified data blocks) of the distributedregister/ledger based on system operator selection.

Referring to FIG. 1, a block diagram is presented of a system 100 forvalidated tracking of equipment during a resource arrangement, inaccordance with embodiments of the present invention. The system 100includes a distributed trust computing network 200 as described in moredetail infra. in relation to FIG. 3. The distributed trust computingnetwork 200 includes a plurality of decentralized nodes 210. Eachdecentralized node 210 having a first memory (not shown in FIG. 1) andat least one first processor (not shown in FIG. 1) in communication withthe first memory. The first memory of the decentralized nodes 210 isconfigured to store at least a portion of a distributed register/ledger220 that includes a plurality of blocks 230-1-230-4. The processors ofdistributed trust computing network 200 are configured tocertify/validate that the data in the blocks 230-1-230-4 is, valid,authentic and unaltered.

The system 100 additionally includes a computing platform 400 disposedwithin a distributed communication network 300, such as the Internetand/or intranets. The computing platform 400 may comprise one or morecomputing devices, for example server(s) or the like. In specificembodiments of the system, the computing platform 400 is under thecontrol of a trusted entity, such as a financial institution, governmentagency or the like. The computing platform 400 includes a second memory402 and at least one second processor 404 in communication with thesecond memory 402.

The second memory stores instructions 410 that are executable by secondprocessor 404. The instructions 410 are configured to receiveindication/notification of resource arrangement 420 associated withequipment 430. Equipment 430 as used herein includes any financed andmoveable property, such as, but not limited to, automobiles,recreational vehicles, boats, industrial equipment, machinery or thelike. In specific embodiments of the invention, equipment 430 is aninventory or portfolio of vehicles financed by a lending entity, such asa financial institution (otherwise referred to herein as the resourceprovider) and in possession of a resale entity, such as automobiledealer (otherwise referred to herein as the equipment possessor).

A resource arrangement 420420 as used herein is a financing agreementbetween a lender (e.g., resource provider) and an equipment possessor(e.g., a vehicle dealer or the like). In specific embodiments of theinvention, in which the equipment 430 is an inventory of vehicles, theresource arrangement 420 includes a demand note issued by the lender tothe vehicle dealer with the inventory of vehicles serving as collateral.In such embodiments of the invention, each unit of inventory (i.e., eachseparate vehicle) has a separate contract that defines the financingobligations and rights of the lending entity and the dealer.

In response to the indication/notification, the instructions 410 arefurther configured to initiate generation of a distributed/registerledger 220 stored within the nodes 210 of the distributed trustcomputing network 200. The distribute register/ledger 220 stores anequipment identifier (ID) 432 that serves to identify the equipmentthroughout the usage duration of the equipment. For example, in thoseembodiments in which the equipment is a vehicle/automobile, theequipment identifier may be the Vehicle Identification Number (VIN),which denotes, where the vehicle was built, the manufacturer, the brand,type of the vehicle, the model year of the vehicle, the plant at whichthe vehicle was assembled and a unique serial number for the vehicle. Inaddition, the distributed ledger 220 stores other equipment information434 and resource arrangement information 422.

In addition, the instructions 410 are configured to determine orotherwise detect that the equipment 430 has incurred a location-changingevent 440. A location-changing event 440 is any movement of theequipment 430 deemed to be significant enough to warrant verification.As previously discussed, various entities, such as, for example, theresource provider in the resource arrangement (i.e., the financingentity) or an indemnification/insurer may have the need to verify theexistence/location of equipment 430 during the life of the resourcearrangement without having to physically visit the location at which theequipment 430 is purported to be located at. In specific embodiments ofthe invention, location-changing events 440, which may be predefined bythe instruction provider/implementer, may be determined/detected basedone or more of transportation data associated with the equipment 430,electronic communication with the GPS-configured equipment 430, trackingdevices/sensors on the equipment 430 (e.g., Onboard Diagnostics (OBD) orthe like) or any other known or future known means for detectingmovement of the equipment 430. In those embodiments of the invention inwhich the equipment 430 includes GPS sensors or other location sensingmechanisms and network connectivity the equipment providesInternet-of-Things (IOT)-type communication with the system 100 in orderto provide real-time location information to instructions 410. Inresponse to determining/detecting the location-changing event 440, thelocation-changing event 440 is registered within the distributed trustcomputing network 200 by creating a first data block 230-X within thedistributed register/ledger 220 that includes information associatedwith the location-changing event 440 (e.g., origin, destination, route,current location and the like). By registering the location-changingevent 440 within the distributed register/ledger 220 of the distributedtrust computing network 200 authenticity (i.e., truthfulness, veracity)of the location-changing event is verified. As a result, entities, suchas financing parties to the financing agreement or insurers) who desireaccurate verified information regarding equipment location, can accessthe distributed trust computing network as a source of truth as to theequipment's location.

Referring to FIG. 2 a block diagram is presented of a system 110 forvalidated tracking and managing of events associated with equipmentduring a usage lifetime, in accordance with embodiments of the presentinvention. Similar to the system 100 shown in FIG. 1, the system 100includes a distributed trust computing network 200 as described in moredetail infra. in relation to FIG. 3. The distributed trust computingnetwork 200 includes a plurality of decentralized nodes 210. Eachdecentralized node 210 having a first memory (not shown in FIG. 2) andat least one first processor (not shown in FIG. 2) in communication withthe first memory. The first memory of the decentralized nodes 210 isconfigured to store at least a portion of a distributed register/ledger220 that includes a plurality of blocks 230-1-230-4. The processors ofdistributed trust computing network 200 are configured tocertify/validate that the data in the blocks 230-1-230-4 is, valid,authentic and unaltered.

The system 100 additionally includes a computing platform 400 disposedwithin a distributed communication network 300, such as the Internetand/or intranets. The computing platform 400 may comprise one or morecomputing devices, for example server(s) or the like. In specificembodiments of the system, the computing platform 400 is under thecontrol of a trusted entity, such as a financial institution, governmentagency or the like. The computing platform 400 includes a second memory402 and at least one second processor 404 in communication with thesecond memory 402.

The second memory stores instructions 412 that are executable by secondprocessor 404. The instructions 412 are configured to initiategeneration of a distributed register/ledger 220 stored within nodes 210of the distributed trust computing network 200 that is associated withequipment 430. The distributed register/ledger 220 stores, at a minimum,an equipment identifier (ID) 432. The equipment 430 may be any financedand movable property, such as, but not limited to, automobile(s),recreational vehicle(s), boat(s), industrial equipment, machinery or thelike. The equipment identifier (ID) 432 that serves to identify theequipment throughout the usage duration of the equipment. For example,in those embodiments in which the equipment is a vehicle/automobile, theequipment identifier may be the Vehicle Identification Number (VIN),which denotes, where the vehicle was built, the manufacturer, the brand,type of the vehicle, the model year of the vehicle, the plant at whichthe vehicle was assembled and a unique serial number for the vehicle. Inthis regard, the equipment ID 432 acts a virtual birth certificatewithin the distributed ledger that authenticates the equipment and itsorigin. The initiation of the distributed register/ledger 220 may be inresponse to the manufacture of the equipment or in response to aresource arrangement, such as a financing agreement between a financeprovider (e.g., a lending or financial institution) and an equipmentholder/finance recipient (e.g., an equipment dealer, theequipment/vehicle buyer or lessee or the like).

In addition, the instructions 412 are configured to determine orotherwise detect an occurrence of a resource arrangement-related event450 associated with a resource arrangement 420 (shown in FIG. 1). Inspecific embodiments of the invention, the resource arrangement 420 is afinancing agreement/loan between a financing entity and an equipmentholder/possessor (e.g., an equipment vehicle dealer, an equipmentbuyer/lessee or the like). For example, the resource arrangement 420 mayinclude, but is not limited to, a consumer loan between a financingentity and an equipment buyer/lessee or a financing agreement (e.g.,demand note or the like) between a financing entity and an equipmentdealer that covers an inventory of vehicles. Theresource-arrangement-related event may be transfer of resources (e.g., apayment) tied to the resource arrangement 420 or the like. In responseto determining/detecting the resource arrangement-related event 450, theresource arrangement-related event 450 is registered within thedistributed trust computing network 200 by creating a first data block230-Y within the distributed register/ledger 220 that includesinformation associated with the resource arrangement-related event 440(e.g., resource transfer type, data, amount and the like).

Further, the instructions are configured to determine or otherwisedetect an occurrence of a property right-related event 460 affectingproperty rights of the equipment 430. In specific embodiments of theinvention, the property right-related event is a transfer in title froma first party to a second party. In response to determining/detectingthe property right-related event 460, the property right-related event460 is registered within the distributed trust computing network 200 bycreating a second data block 230-Z within the distributedregister/ledger 220 that includes information associated with theproperty right-related event 440 (e.g., date of transfer or title,parties to the transfer and the like).

By registering the resource arrangement-related event 450 and theproperty right-related event 460 within the distributed register/ledger220 of the distributed trust computing network 200 authenticity (i.e.,truthfulness, veracity) of the resource arrangement-related event 450and the property right-related event 460 is realized. As a result,entities, such as financing parties to the financing agreement orinsurers) who desire accurate verified information regarding financingagreements, property rights and the like, can access the distributedtrust computing network as a source of truth as to the status of thefinancing agreement and the property's rights.

FIG. 3 is a schematic diagram of an exemplary distributed trustcomputing network 200, in accordance with embodiments of the presentinvention. The distributed trust computing network 200, in otherinstances referred to a blockchain network, is a distributed databasethat maintains, e.g., a list of data records, or the like. In specificembodiments of the invention the data records may include universal tagslinked to data files, which are verified by the distributed trustcomputing network in terms of (i) the authenticity of the data file,and/or (ii) the user associated with the data file (e.g., rightfulpossessor and/or creator of the digital file). The security of the datamaintained within the trust network is enhanced by the distributednature of the network. The distributed trust computing network 200typically includes several decentralized nodes 210, which may be one ormore systems, machines, computers, databases, data stores or the likeoperably connected with one another. In some instances, each of thenodes 210 or multiple nodes 210 are maintained by different entities. Adistributed trust computing network 200 typically works without acentral repository or single administrator.

A distributed trust computing network 200 provides numerous advantagesover traditional storage networks/databases. A large number of thedecentralized nodes 210 of a trust network may reach a consensusregarding the validity of resources or data maintained with a block ofthe distributed trust computing network, in the context of the presentinvention the validity of the location-changing events of equipmentmaintained on a distributed register/ledger 220 or the like.Additionally, when multiple different suspected location-changing eventsof the equipment exist on the distributed register/ledger 220, multipledecentralized nodes 210 can converge on the most recentlocation-changing event, such that the most recent location-changingevent is verified and reflects the current location of the equipment.For example, in the case of equipment location, any decentralized node210 within the distributed trust computing network 200 that stores arecord, such as location-changing event record, can determine within alevel of certainty whether the record can be authenticated/verified andbecome final by confirming that no conflicting records are confirmed bythe distributed trust computing network 200 elsewhere.

The distributed trust computing network 200 typically has two primarytypes of records. The first type is the record type, which consists ofthe actual data stored in a block 230 (shown in FIGS. 1 and 2) within adistributed register/ledger 220. The second type is the block type,which are records that confirm when and in what sequence certain eventsbecame recorded as part of the distributed trust computing network.Records, such as a location-changing event records, and the eventsassociated therewith are created by participants using the distributedtrust computing network in its normal course of business, for example,when a location-changing event is determined/detected, a data block(s)230 is created by users known as “miners” who use specializedsoftware/equipment to create data blocks 230. Holders (also, referred toas users) of a store block 130 of the distributed trust computingnetwork agree to store the data block 230 within the distributed trustcomputing network 200 and the related data clocks 230 are passed aroundto various nodes 210 of the distributed trust computing network 200. A“valid” data block 230 or related event is one that can be validatedbased on a set of rules that are defined by the particular systemimplementing the distributed trust computing network 100. For example,in the case of location-change events, a valid data block is one thatauthenticates data in the data block to which it is linked and/or theuser/creator/owner of the data block and authorizes specificpredetermined entities to access at least a portion of the distributedregister/ledger 220 to gain access to the data contained in the datablock 230.

A distributed trust computing network 200 is typicallydecentralized—meaning that a distributed register/ledger 220 (i.e., adecentralized register/ledger) is maintained on multiple nodes 210 ofthe distributed trust computing network 200. In this regard, one node210 in the distributed trust computing network 200 may have a completeor partial copy of the entire distributed register/ledger 220 or set ofrecords and/or blocks 230 on the distributed trust computing network200. Events are initiated at a node 210 of a distributed trust computingnetwork 200 and communicated to the various other nodes 210 of thedistributed trust computing network 200. Any of the nodes 210 canvalidate the content of a data block 230 or an associated event, add thedata block 230 and/or the contents of the data block 230 to its copy ofthe distributed register/ledger 220, and/or broadcast the detail/data ofthe data block 230, its associated validation (in the form of a block230) and/or other data to other nodes 210. The distributed trustcomputing network 200 shown in FIG. 3 is configured to perform one ormore of the steps or functions performed by the system shown in FIGS. 1and 2, the computing platform shown in FIGS. 5 and 6 and the methodsdescribed by FIGS. 8 and 9.

Referring to FIG. 4 a schematic diagram is presented of systems 100 and110 that details the accessing of data stored in the distributedregister ledger 220 to various different entities. It should be notedthat the system operator entity 500 in control of computing platform 400can control who has access to the distributed ledger 220 and whatportions of the distributed ledger (e.g., which data blocks 230-1 or thelike) the accessing entities are authorized to access. In this regard,system instruction may provide rules as what types of data an entity mayaccess, when an entity may access, and other access-type restrictions.In this regard, some of the authorized entities may be provided accessto the entire distributed register/ledger 220 while other accessingentities may be provided access to only specified predetermined portionsof the distributed register/ledger 220. In the illustrated embodiment ofFIG. 4 the accessing entities are provided access to the distributedregister/ledger 220 and, more specifically, the distributed trustcomputing network 200 via a distributed communication network 300, suchas the Internet and/or one or more intranets or the like. Further,according to the illustrated embodiments of FIG. 4 access to at least aportion of the distributed ledger is provided to the resource provider510 (e.g., the financing entity) in the resource arrangement (e.g.finance agreement). In this regard, the resource provider 510 may accessthe distributed register/ledger 220 to verify the location of equipmentthat they have provided resources for (i.e., financed). For example,verify that the equipment is located at a dealer site and, in someinstances the specific location within the dealer site. In addition, theresource provider 510 may access the distributed register/ledger 220 toverify proper chain of title and/or the occurrence of resource transfers(e.g., payments or the like) pertaining to the resource arrangement(e.g., financing agreement). For example, in the event that the resourceprovider 510 transfers the resource arrangement, in whole or part, toanother resource provider or entity, the other resource provider orentity may assume, in whole or part, the access privileges that wereproved to the resource provider 510.

In addition, according to specific embodiments of the invention, accessto at least a portion of the distributed ledger is provided to anequipment indemnifier 520 (e.g., an insurance company) to verify theexistence/location of the equipment and the like. Moreover, inaccordance with other specific embodiments of the invention, access toat least a portion of the distributed register/ledger 220 is provided tothe resource recipient 530 (e.g., equipment holder/buyer/lease or thelike) in the resource arrangement (e.g., financing agreement) to verifya chain in title of the equipment, or, those in embodiments in which theresource recipient is an equipment dealer to manage their respectiveinventory of equipment at the dealer lot or the like. It should be notedthat the systems 100 and 110 provide for other entities to be providedaccess to at least a portion of the distributed register/ledger 220 ascircumstances dictate.

Referring to FIG. 5 a block diagram is depicted of the computingplatform 400 configured for validated tracking of events associated withequipment during a resource arrangement, in accordance with embodimentsof the present invention. Computing platform 400, which comprise one ormore computing devices (e.g., personal computers, servers or the like),is configured to execute instructions 410, such as algorithms, modules,routines, applications and the like. Computing platform 400 includessecond memory 402, which may comprise volatile and non-volatile memory,such as read-only and/or random-access memory (RAM and ROM), EPROM,EEPROM, flash cards, or any memory common to computing platforms).Moreover, second memory 402 may comprise cloud storage, such as providedby a cloud storage service and/or a cloud connection service.

Further, computing platform 400 also includes at least one secondprocessor 404, which may be an application-specific integrated circuit(“ASIC”), or other chipset, logic circuit, or other data processingdevice. Second processor 404 may execute one or more applicationprogramming interface (APIs) 406 that interfaces with any residentprograms, such as instructions 410 or the like, stored in the secondmemory 402 of the computing platform 400 and any external programs.Second processor 404 may include various processing subsystems (notshown in FIG. 5) embodied in hardware, firmware, software, andcombinations thereof, that enable the functionality of computingplatform 400 and the operability of the computing platform 400 on thedistributed computing network 300 (shown in FIGS. 2 and 3). For example,processing subsystems allow for initiating and maintainingcommunications and exchanging data with other networked devices. For thedisclosed aspects, processing subsystems of second processor 404 mayinclude any subsystem used in conjunction with instructions 410 andrelated tools, routines, sub-routines, algorithms, sub-algorithms,sub-modules thereof.

Computing platform 400 may additionally include a communications module(not shown in FIG. 5) embodied in hardware, firmware, software, andcombinations thereof, that enables electronic communications between thecomputing platform 400 and other network devices, such as those shown inFIGS. 1, 2 and 4. Thus, communication module may include the requisitehardware, firmware, software and/or combinations thereof forestablishing and maintaining a network communication connection with oneor more distributed trust.

Second memory 402 of computing platform 400 stores instructions 410 thatare executable by second processor(s) 404 and configured to receiveindication/notification of resource arrangement 420 associated withequipment 430. The equipment 430 may be any financed and moveableproperty, such as, but not limited to, automobiles, recreationalvehicles, boats, industrial equipment, machinery or the like. Aspreviously discussed, in specific embodiments of the invention,equipment 430 is an inventory or portfolio of vehicles financed by alending entity, such as a financial institution (otherwise referred toherein as the resource provider) and in possession of a resale entity,such as automobile dealer (otherwise referred to herein as the equipmentpossessor).

In specific embodiments of the invention, the resource arrangement 420is a financing agreement between a lender (e.g., resource provider) andan equipment possessor (e.g., a vehicle dealer or the like). In specificembodiments of the invention, in which the equipment 430 is an inventoryof vehicles, the resource arrangement 420, includes a demand note issuedby the lender to the vehicle dealer with the inventory of vehiclesserving as collateral. In such embodiments of the invention, each unitof inventory has a separate contract that defines the financingobligations and rights of the lending entity and the dealer for aparticular vehicle.

In response to the indication/notification, the instructions 410 arefurther configured to initiate generation of a distributedregister/ledger 220 stored within the nodes 210 of the distributed trustcomputing network 200. The distribute register/ledger 220 stores anequipment identifier (ID) 432 that serves to identify the equipmentthroughout the usage duration of the equipment. For example, in thoseembodiments in which the equipment is a vehicle/automobile, theequipment identifier may be the Vehicle Identification Number (VIN),which denotes, where the vehicle was built, the manufacturer, the brand,type of the vehicle, the model year of the vehicle, the plant at whichthe vehicle was assembled and a unique serial number for the vehicle. Inaddition, the distributed ledger 220 stores other equipment information434 and resource arrangement information 422.

In addition, the instructions 410 are configured to determine orotherwise detect that the equipment 430 has incurred a location-changingevent 440. A location-changing event 440 is any movement of theequipment 430 deemed to be significant enough to warrant verification.

Referring to FIG. 7 a schematic/flow diagram 600 is presented of variousdifferent location-changing events 440, in accordance with embodimentsof the present invention. A location-changing event 440-A comprisestransport/movement of the equipment from a first location 610 associatedwith an equipment provider, such an equipment manufacturer to a secondlocation 620 associated with a resource recipient of the resourcearrangement or a holder/possessor of the equipment, such as an equipmentdealer. In other words, location-changing event 440-A entails transportof the equipment from the manufacturer location to a dealerlocation/lot. The second location 620 may comprise a geo-fenced region622 defined by the perimeter of the equipment dealer location/lot or thelike. In specific embodiments of the invention, location-changing event440-B includes transport/movement of the equipment within the geo-fencedregion 622 (e.g., movement within the equipment dealer location/lot),while in other embodiments of the invention, location-changing event440-C includes transport/movement of the equipment outside of thegeo-fenced region 622 (e.g., movement off of the equipment dealerlocation/lot, such as test drive of a vehicle or the like). In furtherembodiments of the invention, location-changing event 440-D includesmovement of the equipment from the second location 620 associated withthe resource recipient of the resource arrangement (e.g., equipmentdealer lot or the like) to a third location 630 associated with atransferred resource recipient of the resource arrangement (e.g.,another equipment dealer lot to which the equipment/vehicle along with,in some embodiments, the resource arrangement is being transferred). Forexample, in certain instances vehicles are swapped or exchanged amongstvehicle dealers for pending sales of a specified vehicle.

As previously discussed, various entities, such as, for example, theresource provider in the resource arrangement (i.e., the financingentity) or an indemnification/insurer may have the need to verify theexistence/location of equipment 430 during the life of the resourcearrangement without having to physically visit the location at which theequipment 430 is purported to be located at. In specific embodiments ofthe invention, location-changing events 440, which may be predefined bythe instruction provider/implementer, may be determined/detected basedone or more of transportation data associated with the equipment 430,electronic communication with the GPS-configured equipment 430, trackingdevices/sensors on the equipment 430 (e.g., Onboard Diagnostics (OBD) orthe like) or any other known or future known means for detectingmovement of the equipment 430. In those embodiments of the invention inwhich the equipment 430 includes GPS sensors or other location sensingmechanisms and network connectivity the equipment providesInternet-of-Things (IOT)-type communication in order to providereal-time information in response to a location-changing event 440. Inresponse to determining/detecting the location-changing event 440, thelocation-changing event 440 is registered within the distributed trustcomputing network 200 by creating a first data block 230-X within thedistributed register/ledger 220 that includes verified locationinformation 232 associated with the location-changing event 440 (e.g.,origin, destination, route, current location and the like). Byregistering the location-changing event 440 within the distributedregister/ledger 220 of the distributed trust computing network 200authenticity (i.e., truthfulness, veracity) of the location-changingevent 440 is verified. As a result, entities, such as financing partiesto the financing agreement or insurers) who desire accurate verifiedinformation regarding equipment location, can access the distributedtrust computing network as a source of truth as to the equipment'slocation.

In other specific embodiments of the invention, the instructions 410 arefurther configured to determine/detect resource arrangement-relatedevents 450 associated with the resource arrangement 420. The resourcearrangement-related events may include a resource transfer 452 (e.g., apayment from the resource recipient to the resource provider) or a titletransfer 454. In response to determining/detecting the resourcearrangement-related event 450, the resource arrangement-related event450 is registered within the distributed trust computing network 200 bycreating a second data block 230-Y within the distributedregister/ledger 220 that includes verified resource arrangement-relatedevent data information 234 associated with the resourcearrangement-related event 450. By registering the resourcearrangement-related event 450 within the distributed register/ledger 220of the distributed trust computing network 200 authenticity (i.e.,truthfulness, veracity) of the resource arrangement-related event 450 isverified.

In related embodiments of the invention, the distributed register/ledger220 may include logic 240, otherwise referred to as a smart contractthat is configured to perform actions in response to predeterminedevents. In specific embodiments of the invention the event may bedetection of a resource arrangement-related event 450, such as titletransfer 454, which signifies that equipment under a resourcearrangement has been conveyed to another entity (i.e., sold, leased orthe like). In specific embodiments of the invention, the resourcearrangement-related event 450 is a title transfer between resourceproviding entities (i.e., financing entities) or between a resourceproviding entity (i.e., financing entity) and a consumer buyer inresponse to the equipment dealer selling equipment/a vehicle to anequipment buyer. In such embodiments of the invention, the dealer isreleased from the security interest in the equipment under the demandnote. In such embodiments of the invention, the action that is performedmay include, but is not limited to, completing obligations 242associated with the outstanding resource arrangement (e.g., automatictransfer of funds to the resource provider (e.g., financing entity) tocomplete obligations under the resource arrangement (i.e., financingagreement)) and generation of documentation 244 associated with resourcearrangement-related event 450 and registration of such documentation 244on the distributed register/ledger 220 and/or initiation ofcommunication of such documentation 244 to one or more designatedthird-party entities. In addition, in those embodiments of the inventionin which the resource arrangement-related event 450 is the sale or leaseof the equipment by the equipment possessor (e.g., vehicle dealer or thelike), the distributed register/ledger 220 associated with theparticular equipment (e.g., specific vehicle) may be closed off fromfurther entries/data blocks and/or access to the distributedregister/ledger 220 may be denied or limited to the previous equipmentpossessor (e.g., the vehicle dealer that sold or leased the vehicle).

Referring to FIG. 6 a block diagram is depicted of the computingplatform 400 configured for validated tracking and managing of eventsassociated with equipment during a usage lifetime, in accordance withembodiments of the present invention. Computing platform 400, whichcomprise one or more computing devices (e.g., personal computers,servers or the like), is configured to execute instructions 410, such asalgorithms, modules, routines, applications and the like. Computingplatform 400 includes second memory 402, which may comprise volatile andnon-volatile memory, such as read-only and/or random-access memory (RAMand ROM), EPROM, EEPROM, flash cards, or any memory common to computingplatforms). Moreover, second memory 402 may comprise cloud storage, suchas provided by a cloud storage service and/or a cloud connectionservice.

Further, computing platform 400 also includes at least one secondprocessor 404, which may be an application-specific integrated circuit(“ASIC”), or other chipset, logic circuit, or other data processingdevice. Second processor 404 may execute one or more applicationprogramming interface (APIs) 406 that interfaces with any residentprograms, such as instructions 410 or the like, stored in the secondmemory 402 of the computing platform 400 and any external programs.Second processor 404 may include various processing subsystems (notshown in FIG. 5) embodied in hardware, firmware, software, andcombinations thereof, that enable the functionality of computingplatform 400 and the operability of the computing platform 400 on thedistributed computing network 300 (shown in FIGS. 2 and 3). For example,processing subsystems allow for initiating and maintainingcommunications and exchanging data with other networked devices. For thedisclosed aspects, processing subsystems of second processor 404 mayinclude any subsystem used in conjunction with instructions 410 andrelated tools, routines, sub-routines, algorithms, sub-algorithms,sub-modules thereof.

Computing platform 400 may additionally include a communications module(not shown in FIG. 6) embodied in hardware, firmware, software, andcombinations thereof, that enables electronic communications between thecomputing platform 400 and other network devices, such as those shown inFIGS. 1, 2 and 4. Thus, communication module may include the requisitehardware, firmware, software and/or combinations thereof forestablishing and maintaining a network communication connection with oneor more distributed trust.

Second memory 402 of computing platform 400 stores instructions 412 thatare executable by second processor(s) 404 and configured to initiategeneration of a distributed register/ledger 220 stored within nodes 210of the distributed trust computing network 200 that is associated withequipment 430. The distributed register/ledger 220 stores, at a minimum,an equipment identifier (ID) 432. The equipment 430 may be any financedand moveable property, such as, but not limited to, automobile,recreational vehicles, boats, industrial equipment, machinery or thelike. The equipment identifier (ID) 432 that serves to identify theequipment throughout the usage duration of the equipment. For example,in those embodiments in which the equipment is a vehicle/automobile, theequipment identifier may be the Vehicle Identification Number (VIN),which denotes, where the vehicle was built, the manufacturer, the brand,type of the vehicle, the model year of the vehicle, the plant at whichthe vehicle was assembled and a unique serial number for the vehicle. Inthis regard, the equipment ID 432 acts a virtual birth certificatewithin the distributed ledger that authenticates the equipment and itsorigin. The initiation of the distributed register/ledger 220 may be inresponse to the manufacture of the equipment or in response to aresource arrangement, such as a financing agreement between a financeprovider (e.g., a lending or financial institution) and an equipmentholder/recipient (e.g., an equipment/vehicle dealer, anequipment/vehicle buyer or lessee or the like).

In addition, the instructions 412 are configured to determine orotherwise detect an occurrence of a resource arrangement-related event450 associated with a resource arrangement 420. In specific embodimentsof the invention, the resource arrangement 420 is a financingagreement/loan between a financing entity and an equipmentholder/possessor (e.g., an equipment vehicle dealer, an equipmentbuyer/lessee or the like). For example, the resource arrangement 420 mayinclude, but is not limited to, a consumer loan between a financingentity and an equipment buyer/lessee or a financing agreement (e.g.,demand note or the like) between a financing entity and an equipmentdealer that covers an inventory of vehicles. Theresource-arrangement-related event may be transfer of resources (e.g., apayment) tied to the resource arrangement 420 or the like. In responseto determining/detecting the resource arrangement-related event 450, theresource arrangement-related event 450 is registered within thedistributed trust computing network 200 by creating a first data block230-Y within the distributed register/ledger 220 that includesinformation associated with the resource arrangement-related event 440(e.g., resource transfer type, data, amount and the like).

Further, the instructions are configured to determine or otherwisedetect an occurrence of a property right-related event 460 affectingproperty rights 462 of the equipment 430. In specific embodiments of theinvention, the property right-related event 460 is a transfer in titlefrom a first party to a second party. In response todetermining/detecting the property right-related event 460, the propertyright-related event 460 is registered within the distributed trustcomputing network 200 by creating a second data block 230-Z within thedistributed register/ledger 220 that includes information associatedwith the property right-related event 440 (e.g., date of transfer ortitle, parties to the transfer and the like).

By registering the resource arrangement-related event 450 and theproperty right-related event 460 within the distributed register/ledger220 of the distributed trust computing network 200 authenticity (i.e.,truthfulness, veracity) of the resource arrangement-related event 450and the property right-related event 460. As a result, entities, such asfinancing parties to the financing agreement or insurers) who desireaccurate verified information regarding financing agreements, propertyrights and the like, can access the distributed trust computing networkas a source of truth as to the status of the financing agreement and theproperty's rights.

In specific embodiments of the invention, instructions 412 are furtherconfigured to generate a virtual registration object 470 associated withthe equipment 430, such as a virtual license plate, which includes avirtual registration identifier 472 and virtual registration information474. In response to creating the virtual registration object 470, theinstructions 412 are further configured to register the virtualregistration object 470 within the distributed trust computing network200 by creating a third data block 23043 within the distributedregister/ledger 220 that includes the virtual registration identifier472 and the virtual registration information 474. By registering thevirtual registration object 470 within the distributed trust computingnetwork 200 the registration object, such as a license plate stayswithout the equipment 430 throughout the usage life of the equipment 430and registrations can be recorded in individual jurisdictions (i.e.,states or the like) as the equipment is moved from one jurisdiction toanother by the rightful possessor.

In additional embodiments of the invention, the instructions 412 areconfigured to generate and store within the distributed register/ledger220 logic 480, otherwise referred to as smart contracts that areconfigured to perform one or more actions as a result of the distributedtrust computing network verifying the occurrence of one or moretriggering events. For example, in specific embodiments of theinvention, logic 480 is stored in the distributed register/ledger 220that is configured to execute a resource transfer 482 (e.g., payments orthe like) in accordance with predetermined resource transferrequirements (e.g., resource transfer due date, title transfer or thelike). In such embodiments of the invention, an occurrence of thepredetermined resource transfer requirements is registered in thedistributed trust computing network 200 by creating a data block withinthe distributed ledger 220 that includes requirements information. Inresponse to registering the occurrence of the predetermined resourcetransfer requirements, the logic 480 is executed to perform the resourcetransfer 482.

In other specific embodiments of the invention, logic 480 is stored inthe distributed register/ledger 220 that is configured to executeaction(s) 484 in response in response to a change in right of possession(i.e., change in title or the like) of the equipment 430. In suchembodiments of the invention, an occurrence of the change in right ofpossession is registered in the distributed trust computing network 200by creating a data block within the distributed ledger 220 that includeschange in right of possession information. In response to registeringthe occurrence the change in right of possession, the logic 480 isexecuted to perform the action(s) (e.g., payoff outstanding balance ofthe resource arrangement or the like).

In further specific embodiments of the invention, logic 480 is stored inthe distributed register/ledger 220 that is configured to executeaction(s) 486 in response in response to satisfying outstandingobligations of the resource arrangement (i.e., payoff the entirety ofthe resource arrangement or the like). In such embodiments of theinvention, an occurrence of the satisfaction of the outstandingobligations of the resource arrangement is registered in the distributedtrust computing network 200 by creating a data block within thedistributed ledger 220 that includes satisfaction of the outstandingobligations of the resource arrangement information. In response toregistering the occurrence the change in right of possession, the logic480 is executed to perform the action(s) (e.g., transfer the title orthe like).

In further specific embodiments of the invention, logic 480 is stored inthe distributed register/ledger 220 that is configured to executethird-party resource provisioning action(s) 488 in response in responseto a predetermined event. In such embodiments of the invention, anoccurrence of the event is registered in the distributed trust computingnetwork 200 by creating a data block within the distributed ledger 220that includes event information. In response to registering theoccurrence the event, the logic 480 is executed to perform thethird-party resource provisioning action (e.g., transfer pf resource tothe third-party). The predetermined events may include, but are notlimited to an inspection/assessment of the equipment, a due data forregistration associated with the equipment, a due date forinsurance/indemnity premium on the equipment or the like, In addition totriggering, the resource provisioning, the logic 480 may be configuredto perform other actions, such as communicating information to otherthird-parties or the like.

In further embodiment of the invention, the instructions 412 areconfigured to receive maintenance records related to maintenance,including upkeep or repair, performed on the equipment and, in response,register the maintenance event within the distributed trust computingnetwork 200 by creating a data block within the distributed ledger 220that includes maintenance-related information.

Referring to FIG. 8 a flow diagram is presented of a method 700 forvalidated tracking of events associated with equipment during a resourcearrangement, in accordance with embodiments of the present invention. AtEvent 710, indication/notification of resource arrangement associatedwith equipment is received. The equipment may be any financed andmoveable property, such as, but not limited to, automobiles,recreational vehicles, boats, industrial equipment, machinery or thelike. In specific embodiments of the invention, equipment 430 is aninventory or portfolio of vehicles financed by a lending entity, such asa financial institution (otherwise referred to herein as the resourceprovider) and in possession of a resale entity, such as automobiledealer (otherwise referred to herein as the equipment possessor).

In specific embodiments of the invention, the resource arrangement is afinancing agreement between a lender (e.g., resource provider) and anequipment possessor (e.g., a vehicle dealer or the like). In specificembodiments of the invention, in which the equipment 430 is an inventoryof vehicles, the resource arrangement 420 includes a demand note issuedby the lender to the vehicle dealer with the inventory of vehiclesserving as collateral. In such embodiments of the invention, each unitof inventory (i.e., each separate vehicle) has a separate contract thatdefines the financing obligations and rights of the lending entity andthe dealer.

In response to the receiving the indication/notification of the resourcearrangement, at Event 720, generation of a distributed register/ledgerassociated with the equipment is stored a distributed trust computingnetwork is initiated. The distribute register/ledger stores an equipmentidentifier (ID) that serves to identify the equipment throughout theusage duration of the equipment. For example, in those embodiments inwhich the equipment is a vehicle/automobile, the equipment identifiermay be the Vehicle Identification Number (VIN), which denotes, where thevehicle was built, the manufacturer, the brand, type of the vehicle, themodel year of the vehicle, the plant at which the vehicle was assembledand a unique serial number for the vehicle. In addition, the distributedledger stores other equipment information and resource arrangementinformation.

At Event 730, a location-changing event incurred by the equipment isdetermined or otherwise detected. As previously discussed, alocation-changing event is any movement of the equipment deemed to besignificant enough to warrant verification. As previously discussed,various entities, such as, for example, the resource provider in theresource arrangement (i.e., the financing entity) or anindemnification/insurer may have the need to verify theexistence/location of equipment during the life of the resourcearrangement without having to physically visit the location at which theequipment is believed to be located. In specific embodiments of theinvention, location-changing events, which may be predefined by theinstruction provider/implementer, may be determined/detected based oneor more of transportation data associated with the equipment, electroniccommunication with the GPS-configured equipment, trackingdevices/sensors on the equipment (e.g., Onboard Diagnostics (OBD) or thelike) or any other known or future known means for detecting movement ofthe equipment. Location-changing events may include but are, not limitedto (i) physical movement of the equipment from a first locationassociated with an equipment provider to a second location associatedwith a resource recipient of the resource arrangement, (ii) physicalmovement of the equipment within a geo-fenced region defined by alocation associated with a resource recipient of the resourcearrangement, (iii) physical movement of the equipment outside of ageo-fenced region defined by a location associated with a resourcerecipient of the resource arrangement, and (iv) physical movement of theequipment from a first location associated with a first resourcerecipient of the resource arrangement to a second location associatedwith a transferred resource recipient of the resource arrangement.

In response to determining/detecting the location-changing event, atEvent 740, the location-changing event is registered within thedistributed trust computing network by creating a first data blockwithin the distributed register/ledger that includes informationassociated with the location-changing event (e.g., origin, destination,route, current location and the like). By registering thelocation-changing event within the distributed register/ledger of thedistributed trust computing network authenticity (i.e., truthfulness,veracity) of the location-changing event is verified. As a result,entities, such as financing parties to the financing agreement orinsurers) who desire accurate verified information regarding equipmentlocation, can access the distributed trust computing network as a sourceof truth as to the equipment's location.

Referring to FIG. 9 a flow diagram is depicted of a method 800 forvalidated tracking and managing of events associated with equipmentduring the usage lifetime, in accordance with embodiment of the presentinvention. At Event 810, generation of a distributed register/ledgerassociated with equipment is initiated and the register/ledger is storedwithin nodes of the distributed trust computing network. The distributedregister/ledger stores, at a minimum, an equipment identifier (ID). Theequipment may be any financed and moveable property, such as, but notlimited to, automobile(s), recreational vehicle(s), boat(s), industrialequipment, machinery or the like. The equipment identifier (ID) thatserves to identify the equipment throughout the usage duration of theequipment. For example, in those embodiments in which the equipment is avehicle/automobile, the equipment identifier may be the VehicleIdentification Number (VIN), which denotes, where the vehicle was built,the manufacturer, the brand, type of the vehicle, the model year of thevehicle, the plant at which the vehicle was assembled and a uniqueserial number for the vehicle. In this regard, the equipment ID acts avirtual birth certificate within the distributed ledger thatauthenticates the equipment and its origin. The initiation of thedistributed register/ledger may be in response to the manufacture of theequipment or in response to a resource arrangement, such as a financingagreement between a finance provider (e.g., a lending or financialinstitution) and an equipment holder/recipient (e.g., anequipment/vehicle dealer, the equipment/vehicle buyer or lessee or thelike).

At Event 820, an occurrence of a resource arrangement-related eventassociated with a resource arrangement is determined or otherwisedetected. In specific embodiments of the invention, the resourcearrangement is a financing agreement/loan between a financing entity andan equipment holder/possessor (e.g., an equipment vehicle dealer, anequipment buyer/lessee or the like). For example, the resourcearrangement may include, but is not limited to, a consumer loan betweena financing entity and an equipment buyer/lessee or a financingagreement (e.g., demand note or the like) between a financing entity andan equipment dealer that covers an inventory of vehicles. Theresource-arrangement-related event may be transfer of resources (e.g., apayment) tied to the resource arrangement or the like.

In response to determining/detecting the resource arrangement-relatedevent, at Event 830, the resource arrangement-related event isregistered within the distributed trust computing network by creating afirst data block within the distributed register/ledger that includesinformation associated with the resource arrangement-related event(e.g., resource transfer type, data, amount and the like).

At Event 840, an occurrence of a property right-related event isdetermined or otherwise detected that affects property rights of theequipment. In specific embodiments of the invention, the propertyright-related event is a transfer in title from a first party to asecond party. In response to determining/detecting the propertyright-related event, at Event 850, the property right-related event isregistered within the distributed trust computing network by creating asecond data block within the distributed register/ledger that includesinformation associated with the property right-related event (e.g., dateof transfer or title, parties to the transfer and the like).

By registering the resource arrangement-related event and the propertyright-related event within the distributed register/ledger of thedistributed trust computing network authenticity of the resourcearrangement-related event and the property right-related event isrealized. As a result, entities, such as financing parties to thefinancing agreement or insurers) who desire accurate verifiedinformation regarding financing agreements, property rights and thelike, can access the distributed trust computing network as a source oftruth as to the status of the financing agreement and the property'srights.

Thus, present embodiments of the invention provide for tracking andmanaging of events associated with equipment during a usage lifetime.The invention provides for registering an equipment identifier within adistributed register/ledger of a distributed trust network andsubsequently registering and managing events associated with theequipment during the usage lifetime. In specific embodiments of theinvention, such events include resource arrangement-related events andproperty-right-related events. In addition, logic may be included in thedistributed register/leger that triggers various actions in response tothe events.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible.

Those skilled in the art may appreciate that various adaptations andmodifications of the just described embodiments can be configuredwithout departing from the scope and spirit of the invention. Therefore,it is to be understood that, within the scope of the appended claims,the invention may be practiced other than as specifically describedherein.

INCORPORATION BY REFERENCE

To supplement the present disclosure, this application furtherincorporates entirely by reference the following commonly assignedpatent applications:

U.S. patent application Ser. No. Title Filed On 16/831,335 SYSTEM FORVALIDATED TRACKING Mar. 26, 2020 OF EVENTS ASSOCIATED WITH EQUIPMENTDURING A RESOURCE ARRANGEMENT 16/831,447 SYSTEM FOR TRACKING A RESOURCEMar. 26, 2020 MAINTENANCE AND RESOURCE CAPABILITIES 16,831,467 SYSTEMFOR TRACKING A RESOURCE Mar. 26, 2020 PERFORMANCE AND MAINTENANCE16/831,372 SYSTEM FOR TRACKING RESOURCES Mar. 26, 2020 WITH MULTIPLEUSERS AND MULTIPLE LOCATIONS

What is claimed is:
 1. A system for validated tracking and managing of events associated with a vehicle, the system comprising: at least one distributed trust computing network comprising a plurality of decentralized nodes, each decentralized node having a first memory and at least one first processor in communication with the memory, wherein the first memory of the decentralized nodes is configured to store at least one distributed register comprising a plurality of blocks of data; and a computing platform disposed in a distributed computing network and including a second memory and at least one second processing device in communication with the second memory, wherein the second memory stores instructions executable by the at least one second processing device and configured to: initiate generation of a distributed register stored within the distributed trust computing network and associated with a vehicle, wherein the distributed register stores a Vehicle Identifier Number (VIN) associated with the vehicle, determine an occurrence of a resource arrangement-related event associated with a resource arrangement, wherein the resource arrangement is between a resource provider and a resource recipient for purposes of possessing the vehicle, in response to determining the occurrence of the resource arrangement-related event, register the resource arrangement-related event with the distributed trust computing network by creating a first block within the distributed register that includes information associated with the resource arrangement-related event, determine an occurrence of a property right event affecting property rights of the vehicle, in response to determining the occurrence of the property right event, register the property right event with the distributed trust computing network by creating a second block within the distributed register that includes information associated with the property right event, generate a virtual registration object for the vehicle, wherein the virtual registration object is a virtual license plate and includes a virtual registration identifier and virtual registration information, and register the virtual registration object with the distributed trust computing network by creating a third block within the distributed register that includes the virtual registration identifier and the virtual registration information, wherein the registering of the resource arrangement-related event, the property right event and the virtual registration object within the distributed trust computing network provides for validating authenticity of the resource arrangement-related event, the property right event and the virtual registration object.
 2. The system of claim 1, wherein the instructions are further configured to: store, in the distributed register, logic configured to execute resource transfers from the resource provider to the resource recipient in accordance with predetermined requirements of the resource arrangement, register, in the distributed register, an occurrence of the predetermined requirements being met by creating a third block within the distributed register that includes requirements information, and in response to registering the occurrence of the predetermined requirements being met in the distributed register, execute the logic.
 3. The system of claim 1, wherein the instructions are further configured to: store, in the distributed register, logic configured to execute one or more actions in response to satisfying outstanding resource obligations of the resource arrangement, register, in the distributed register, an occurrence of a satisfaction of the outstanding resource obligations of the resource arrangement by creating a third block within the distributed register that includes satisfaction of the outstanding resource obligation information, and in response to registering the satisfaction of the outstanding resource obligations in the distributed register, execute the logic to perform the one or more actions.
 4. The system of claim 1, wherein the instructions are further configured to: store, in the distributed register, logic configured to perform one or more actions in response to a change in right of possession of the vehicle, register, in the distributed register, a change in the right of possession by creating a third block within the distributed register that includes right of possession information, and in response to registering the change in the right of possession in the distributed ledger, execute the logic to perform the one or more actions.
 5. The system of claim 1, wherein the instructions are further configured to: store, in the distributed register, logic configured to provide resources to a third-party in response to a predetermined event, register, in the distributed register, an occurrence of the predetermined event by creating a third block within the distributed register that includes predetermined event information, and in response to registering the occurrence of the predetermined event in the distributed register, execute the logic to provide resources to the third-party.
 6. The system of claim 5, wherein the predetermined event is a scheduled due date for one of (i) an assessment placed on the vehicle, (ii) a registration associated with the vehicle, and (iii) an insurance premium for the vehicle.
 7. A computer-implemented method for validated tracking and managing of events associated with a vehicle, the method is executable by one or more computer processor devices and comprises: initiating generation of a distributed register within a distributed trust computing network and associated with a vehicle an equipment, wherein the distributed register stores an equipment identifier a Vehicle Identifier Number (VIN) associated with the vehicle; determining an occurrence of a resource arrangement-related event associated with a resource arrangement, wherein the resource arrangement is between a resource provider and a resource recipient for purposes of possessing the vehicle; in response to determining the occurrence of the resource arrangement-related event, registering the resource arrangement-related event with the distributed trust computing network by creating a first block within the distributed register that includes information associated with the resource arrangement-related event; determining an occurrence of a property right event affecting property rights of the vehicle; in response to determining the occurrence of the property right event, registering the property right event with the distributed trust computing network by creating a second block within the distributed register that includes information associated with the property right event; generating a virtual registration object for the vehicle, wherein the virtual registration object is a virtual license plate and includes a virtual registration identifier and virtual registration information; and registering the virtual registration object with the distributed trust computing network by creating a third block within the distributed register that includes the virtual registration identifier and the virtual registration information, wherein the registering of the resource arrangement-related event the property right event and the virtual registration object within the distributed trust computing network provides for validating authenticity of the resource arrangement-related event, the property right event and the virtual registration object.
 8. The computer-implemented method of claim 7, further comprising: storing, in the distributed register, logic configured to execute resource transfers from the resource provider to the resource recipient in accordance with predetermined requirements of the resource arrangement; registering, in the distributed register, an occurrence of the predetermined requirements being met by creating a third block within the distributed register that includes requirements information; and in response to registering the occurrence of the predetermined requirements being met in the distributed register, executing the logic to transfer resources from the resource provider to the resource recipient.
 9. The computer-implemented method of claim 7, further comprising: storing, in the distributed register, logic configured to execute one or more actions in response to satisfying outstanding resource obligations of the resource arrangement; registering, in the distributed register, an occurrence of a satisfaction of the outstanding resource obligations of the resource arrangement by creating a third block within the distributed register that includes satisfaction of the outstanding resource obligation information; and in response to registering the satisfaction of the outstanding resource obligations in the distributed register, executing the logic to perform the one or more actions.
 10. The computer-implemented method of claim 7, further comprising: storing, in the distributed register, logic configured to perform one or more actions in response to a change in right of possession of the vehicle; registering, in the distributed register, a change in the right of possession by creating a third block within the distributed register that includes right of possession information; and in response to registering the change in the right of possession in the distributed ledger, executing the logic to perform the one or more actions.
 11. The computer-implemented method of claim 7, further comprising: storing, in the distributed register, logic configured to provide resources to a third-party in response to a predetermined event; registering, in the distributed register, an occurrence of the predetermined event by creating a third block within the distributed register that includes predetermined event information; and in response to registering the occurrence of the predetermined event in the distributed register, executing the logic to provide resources to the third-party.
 12. The computer-implemented method of claim 11, wherein the predetermined event is a scheduled due date for one of (i) an assessment placed on the vehicle, (ii) a registration associated with the vehicle, and (iii) an insurance premium for the vehicle.
 13. A computer program product comprising a non-transitory computer-readable medium including: a first set of codes for causing a computer processor to initiating generation of a distributed register within a distributed trust computing network and associated with a vehicle, wherein the distributed register stores a Vehicle Identifier Number (VIN) associated with the vehicle; a second set of codes for causing a computer processor to determine an occurrence of a resource arrangement-related event associated with a resource arrangement, wherein the resource arrangement is between a resource provider and a resource recipient for purposes of possessing the vehicle; a third set of codes for causing a computer processor to, in response to determining the occurrence of the resource arrangement-related event, register the resource arrangement-related event with the distributed trust computing network by creating a first block within the distributed register that includes information associated with the resource arrangement-related event; a fourth set of codes for causing a computer processor to determine an occurrence of a property right event affecting property rights of the vehicle; a fifth set of codes for causing a computer processor to, in response to determining the occurrence of the property right event, register the property right event with the distributed trust computing network by creating a second block within the distributed register that includes information associated with the property right event; a sixth set of codes for causing a computer processor to generate a virtual registration object for the vehicle, wherein the virtual registration object is a virtual license plate and includes a virtual registration identifier and virtual registration information; and a seventh set of codes for causing a computer processor to register the virtual registration object with the distributed trust computing network by creating a third block within the distributed register that includes the virtual registration identifier and the virtual registration information, wherein the registering of the resource arrangement-related the property right event and the virtual registration object within the distributed trust computing network provides for validating authenticity of the resource arrangement-related event, the property right event and the virtual registration object.
 14. The computer program product of claim 13, further comprising: an eighth set of codes for causing a computer processor to store, in the distributed register, logic configured to execute resource transfers from the resource provider to the resource recipient in accordance with predetermined requirements of the resource arrangement; a ninth set of codes for causing a computer processor to register, in the distributed register, an occurrence of the predetermined requirements being met by creating a third block within the distributed register that includes requirements information; and a tenth set of codes for causing a computer processor to, in response to registering the occurrence of the predetermined requirements being met in the distributed register, executing the logic to transfer resources from the resource provider to the resource recipient.
 15. The computer program product of claim 13, further comprising: an eighth set of codes for storing, in the distributed register, logic configured to execute one or more actions in response to satisfying outstanding resource obligations of the resource arrangement; a ninth set of codes for causing a computer processor to register, in the distributed register, an occurrence of a satisfaction of the outstanding resource obligations of the resource arrangement by creating a third block within the distributed register that includes satisfaction of the outstanding resource obligation information; and a tenth set of codes for causing a computer to, in response to registering the satisfaction of the outstanding resource obligations in the distributed register, execute the logic to perform the one or more actions.
 16. The computer program product of claim 13, further comprising: an eighth of codes for causing a computer processor to store, in the distributed register, logic configured to perform one or more actions in response to a change in right of possession of the vehicle; a ninth of codes for causing a computer processor to register, in the distributed register, a change in the right of possession by creating a third block within the distributed register that includes right of possession information; and a tenth set of codes for causing a computer processor to, in response to registering the change in the right of possession in the distributed ledger, execute the logic to perform the one or more actions.
 17. The computer program product of claim 13, further comprising: an eighth of codes for causing a computer processor to store, in the distributed register, logic configured to provide resources to a third-party in response to a predetermined event; a ninth set of codes for causing a computer processor register, in the distributed register, an occurrence of the predetermined event by creating a third block within the distributed register that includes predetermined event information; and a tenth set of codes for causing a computer processor to, in response to registering the occurrence of the predetermined event in the distributed register, execute the logic to provide resources to the third-party. 